Home
News
Translation
Project
Forum
Help
Members
Log in
Register
. .
•Profile
kadirbedir
•All translations
▪▪Requested translations
•
Mīļākie tulkojumi
•List of projects
•Inbox
▪Free language exchange
•English
•Türkçe
•Français
•Español
•Italiano
•Português brasileiro
•Deutsch
•Română
•عربي
•Русский
•Svenska
•Ελληνικά
•Български
•עברית
•Shqip
•Srpski
•Nederlands
•Dansk
•Português
•Polski
•汉语(简体)
•Lietuvių
•Norsk
•فارسی
•Suomi
•Hrvatski
•日本語
•Català
•Esperanto
•한국어
•Українська
•Føroyskt
•नेपाली
•Kiswahili
All translations
Search
Requested translations - kadirbedir
Search
Source language
Target language
Results 1 - 2 of about 2
1
719
Source language
Šis tulkojums pieprasa tikai nozīmi.
Object Diagrams An object diagram models the...
Object Diagrams
An object diagram models the objects in a system at some specific point in time. The
term snapshot is sometimes applied to object diagrams, because they can be thought
of as being like photographs that show exactly what things were like when the
snapshot was taken.
In analysis, we can use sequences of object diagrams to show how actions change the
state of the system – by creating new objects, changing their attribute values, inserted
them into relationships with other objects and so on.Object diagrams are woefully underutilized in many projects.
The important things to remember about object diagrams are:
• They are good for “collecting data” on a business problem
• They are good for understanding how actions effect objects
• They are good for testing our models – they are the UML equivalent of test
data
Completed translations
Nesne Şemaları
1